This is testing my upstreaming branch. We are mapping out the update process - Adrien described a way to add the new version dependencies to the packages prior to release which Spack would interpret as using develop. We then would just add the commit hash for each tag once the releases are published to GitHub.

Would please ask Adrien to upstream the packages changes for the v2025.12.x RAJA Suite release and then (via webex, RSC documentation, etc.) have him or you walk us through the process so we are all on the same page? Thank you.

@rhornung67 I’ll work on describing the new process after the holidays.
When it comes to the 2025.12 release, if the present attempt succeeds in time, we can make the packages update directly in spack-packages. I’ll work on that tomorrow and on Friday once the Gitlab Component stuff is merged.

@davidbeckingsale building went well. (Be mindful that the tests are not run).
The failures were due to a known issue with sharing a spack instance with many builds. For some reason, rajaperf is more sensitive to this. I just restarted those jobs (after restarting the shared alloc and shared spack creation).

@davidbeckingsale @rhornung67 @tdrwenski
This is ready for review and merge.

This PR completes the removal of local spack packages, moving maintenance to spack/spack-packages directly.

I updated the spack-packages reference to point at the merge commit of spack/spack-packages#3279.